home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Experimental BBS Explossion 3
/
Experimental BBS Explossion III.iso
/
gus
/
sdkdigv9.zip
/
SDKV9N29.TXT
< prev
next >
Wrap
Text File
|
1994-03-18
|
4KB
|
96 lines
Apparently-To: john.smith@gravis.com
GUS Programmer's Digest Thu, 17 Mar 94 17:07 PST Volume 9: Issue 29
Today's Topics:
No midi input in windows
Standard Info:
- Meta-info about the GUS can be found at the end of the Digest.
- Before you ask a question, please READ THE FAQ.
----------------------------------------------------------------------
Date: Thu, 17 Mar 1994 09:43:45 +0100
From: A.PAUW@elsevier.nl
Subject: No midi input in windows
I have a following question related to a non-working midi
input in Windows.
I have installed in my machine (486SX/33) two soundcards: a
SoundBlaster 2.0 and (of course) a GUS rev. 3.7. They both
work, using the following setup:
SB address 220h, DMA 1 (fixed), IRQ 5
GUS address 240h, DMA 3 (GF1 DMA), IRQ 7 (midi), GF1 IRQ 11
I have no problems of working with it because I don't use it
for any games and work mostly in Windows. Both wave devices
(SB in/out, GUS in/out) are accessable as are the MIDI
devices (SB and GUS). The MIDI port of the SoundBlaster
works both in and out, the MIDI port of the GUS doesn't do
input (although both the synthesizer devices SB and GUS work).
The MIDI port does work in DOS and as I found out, the NMI
on my mainboard doesn't work. I know, one would say buy a
better mainboard, but can anyone tell me WHY this doesn't
work. I know that handling interrupts in Windows is a bit
tricky because of the timing/delay problems running in
Windows in enhanced mode, but the SoundBlaster has no
problems with it. Doesn't the GUS have an internal buffer
to prefent input overflow? Are there any homebrew drivers
available that DO work without problems? Maybe by running
the MIDI port in the MPU-401 compatible mode?
Am I correct to assume that the I/O addresses of the GUS
have 'shadow' address like
220h (shadowed 320h, 420h)
230h (shadowed 330h, 430h)
240h (shadowed 340h, 440h)
The 401 driver which comes with Windows has a limited address
setup range (the standard 330h address), but when I changed
the I/O address of my GUS to 230h (shadowed on 330h I
presume) then Windows has big problems and won't start, I
haven't figured out yet why and changed it back to 340h, it
works again. So it looks like I can't use the standard 401
driver of Windows.
Has anyone suggestions? (Except changing the motherboard,
of all programs and I/O cards I use(d) only the GUS gives
this problem, so why change?).
Thanks for your help.
Albert Pauw
a.pauw@elsevier.nl
------------------------------
End of GUS Programmer's Digest V9 #29
*************************************
To post to tomorrow's digest: <gus-sdk@mail.orst.edu>
To (un)subscribe or get help: <gus-sdk-request@mail.orst.edu>
To contact a human (last resort): <gus-sdk-owner@mail.orst.edu>
FTP Sites Archive Directories
--------- ------- -----------
Main N.American Site: archive.orst.edu pub/packages/gravis
wuarchive.wustl.edu systems/ibmpc/ultrasound
Main Asian Site: nctuccca.edu.tw PC/ultrasound
European Callers ONLY: theoris.rz.uni-konstanz.de pub/sound/gus
Submissions: archive.epas.utoronto.ca pub/pc/ultrasound/submit
Newly Validated Files: archive.epas.utoronto.ca pub/pc/ultrasound
Mirrors: garbo.uwasa.fi mirror/ultrasound
MailServer For Archive Access: Email to <mail-server@nike.rz.uni-konstanz.de>
Hints:
- Get the FAQ from the FTP sites or the request server.
- Mail to <gus-sdk-request@mail.orst.edu> for info about other GUS
related mailing lists (general use, musician's, etc.).